Blockchain augmented internet of things (“IoT”) device-based system for dynamic supply chain tracking

ABSTRACT

Systems and methods for dynamic supply chain product tracking are provided. The method may include embedding IoT devices across a multi-stage supply chain. The method may include computing, via the IoT devices, a value impact of each stage of the multi-stage supply chain process. The method may also include transmitting, via the IoT devices, each value impact of a stage to blockchain database host systems. The method may also include constructing, via each of the blockchain database host systems, a new linked data block for each value impact of a stage. The method may also include computing a real value of the end product based on the linked data blocks in the blockchain database host systems.

FIELD OF TECHNOLOGY

Aspects of the disclosure relate to Internet of Things (“IoT”) devices.Specifically, aspects of the disclosure relate to networks of IoTdevices augmented with blockchain technology.

BACKGROUND OF THE DISCLOSURE

A supply chain may be used to manufacture components and form unitassemblies. Examples of unit assemblies include a finished unitprocessed from a single component, or a combination of multiplecomponents connected or affixed into a larger unit. At the end of asupply chain, a unit assembly, referred to herein, in the alternative,simply as a unit, represents a final product.

For example, a driver's-side airbag is a unit assembly of componentswhich themselves are assemblies of other, more basic subcomponents. Theairbag assembly is itself a unit which might be part of a larger unitassembly such as a car.

A complete supply chain—i.e., source and manufacturing—lifecycle forassembling a final product typically begins with raw material. The rawmaterial may be sourced, purchased, or created by a first entity. As theraw material travels down the supply chain, it undergoes physical andtransactional transformations. For example, the raw material may be soldto a second entity, which may proceed to mold the raw material into asubcomponent. The second entity may sell the subcomponent to a thirdentity, which may build the subcomponent into a larger component.Building the subcomponent into a larger component may be a part of alarger process—at the third entity—to manufacture a final product.

In another example, a single entity may oversee the entire supply chainlifecycle. In yet another example, the raw material may be processedindividually throughout a supply chain lifecycle, without joining othersubcomponents.

It is often desirable for a manufacturer of a final product tounderstand and monitor the source of, and the process undergone by, allcomponents (and subcomponents) included in a particular unit assembly.Variations in the source and process can have significant impact on theaggregate end value of a product. For example, a car built by a carmanufacturer may have a range of actual costs depending on the whichsources were used for particular raw materials, components, andsubcomponents. The unique supply chain experience of an individual carmay also affect the value of the car. For example, if a component wasfound to be faulty and required replacement, or a mishap on the assemblyline caused a delay in the manufacturing process, that individual carmay be associated with a higher production cost.

Safety and quality may be a concern as well. For example, it may beimportant to understand the source of components and the specificprocesses used to construct a particular driver's-side airbag, aparticular jet engine, or a particular medical implant. Understandingthe source and process may be crucial to obtaining an accurate safetyand/or quality rating for a specific product.

This is difficult, in practice, because each particular product may havea long and complex supply chain history. The history may includemultiple entities, such as sources and/or suppliers. Each entity mayhave their own historical records, or may not maintain records at all.Furthermore, the history may contain many phases of a supply chainprocess, each phase contributing to the final, actual product. Eachphase may be associated with a variable cost.

The Internet of Things (“IoT”) is a distributed network of devices,including small and micro devices, that are connected—directly orindirectly—to the internet. A blockchain is a distributed ledger ofrecords which contain information.

It would be desirable to provide systems and methods for providing IoTdevice-based supply chain valuation. It would be further desirable toaugment management of the system with blockchain technology.

SUMMARY OF THE DISCLOSURE

Aspects of the disclosure relate to smart supply chains. The smartsupply chain (“SSC”) may include a plurality of stages. Each stage maybe configured to execute one step of a multi-step process. Themulti-step process may be for producing an end product from one or moresub-products.

The SSC may include a plurality of IoT devices. Each one of the IoTdevices may either be associated with a stage or coupled to a product. Aproduct may be the end product or one of the sub-products.

The SSC may include a blockchain database. The blockchain database mayinclude a plurality of coordinated databases. Each coordinated databasemay be stored on a distinct node from a plurality of nodes. Eachcoordinated database may include linked blocks of hashed data. A blockthat is linked to a previous block may include a hashing of the hasheddata of the previous block.

The IoT devices of the SSC may compute a record for each step of themulti-step process. The record may include data that includes a stepidentifier (“ID”) and a calculation of a value impact of the step. Thedata may be added to the blockchain database. The end product may beassociated with a real value that is based on the data in the blockchaindatabase.

BRIEF DESCRIPTION OF THE DRAWINGS

The objects and advantages of the disclosure will be apparent uponconsideration of the following detailed description, taken inconjunction with the accompanying drawings, in which like referencecharacters refer to like parts throughout, and in which:

FIG. 1 shows an illustrative system in accordance with principles of thedisclosure;

FIG. 2 shows another illustrative system in accordance with principlesof the disclosure;

FIG. 3 shows yet another illustrative system in accordance withprinciples of the disclosure;

FIG. 4 shows still another illustrative system in accordance withprinciples of the disclosure;

FIG. 5 shows another illustrative system in accordance with principlesof the disclosure;

FIG. 6 shows yet another illustrative system in accordance withprinciples of the disclosure;

FIG. 7 shows an illustrative flowchart in accordance with principles ofthe disclosure; and

FIG. 8 shows an illustrative system in accordance with principles of thedisclosure.

DETAILED DESCRIPTION OF THE DISCLOSURE

Aspects of the disclosure relate to smart supply chains. The smartsupply chain (“SSC”) may include a plurality of stages. Each stage maybe configured to execute one step of a multi-step process. Themulti-step process may be for producing an end product from one or moresub-products.

The SSC may include a plurality of IoT devices. Each one of the IoTdevices may be associated with a stage or coupled to a product (i.e.,the end product or one of the sub-products).

An IoT device associated with a stage may include physical proximity toa stage, e.g., a device with a sensor that is near a machine on anassembly line. It may also include virtual association, e.g., a devicethat tracks purchase costs of a set of components. An IoT device coupledto a product may include any suitable means for attaching any suitabledevice to the product. In one illustrative example, the IoT device maybe a small unit with basic memory, processing, and/ortransmitting/receiving functionality. The small device may include anadhesive for affixing to the product. In one example, the small unit maybe microscopic.

The SSC may include a blockchain database. The blockchain database mayinclude a plurality of coordinated (i.e., synced via consensus)databases. Each coordinated database may be stored on a distinct nodefrom a plurality of nodes. Each coordinated database may include linkedblocks of hashed data. A block that is linked to a previous block mayinclude a hashing of the hashed data of the previous block. In certainembodiments, the data may be encrypted. In other embodiments, the datamay not be hashed or encrypted.

The IoT devices of the SSC may compute a record for each step of themulti-step process. The record may include data that includes a stepidentifier (“ID”), a calculation of a value impact of the step, and/orany other suitable information. The data may be added to the blockchaindatabase. The end product may be associated with a real value that isbased on the data in the blockchain database.

In some embodiments of the SSC, the value impact of a step may include asum of the values of a plurality of sub-products that are merged at thestep. For example, when a seatback and lower-seat are merged in anautomotive supply chain, the value of the seatback (contained in an IoTdevice coupled to the seatback) may be summed with the value of thelower-seat (contained in an IoT device coupled to the lower-seat) togive a value of the merged chair. The value impact may include anincrease in value due to an improvement executed on a product at thestep. For example, if a cost was expended to merge the seatback andlower-seat, the value impact of the merged chair may be a sum of thevalues of the seatback and lower-seat plus the cost of merging. Thevalue impact may include a decrease in value due to an occurrence at thestep. For example, if a component got damaged at a step, the value ofthe component may decrease. In this example, the value may reflect anintrinsic value as opposed to a cost to the manufacturer.

In certain embodiments of the SSC, when an IoT device records a step,the IoT device may add the data of the step to the blockchain database.Adding the data may include transmitting the data to the plurality ofnodes. Each node may hash the data. The hashed data may be stored as anew linked block.

The nodes of the SSC may comprise the IoT devices. The nodes maycomprise computer systems of one or more preauthorized entities.Entities may include suppliers, manufacturers, distributers, retailers,regulatory agencies, or any other suitable entity. In some embodiments,a consortium of entities may form to host the blockchain.

A system for dynamic valuation of a unit is provided. The unit may bemanufactured via a multi-stage supply chain process. The unit mayinclude one or more subunits. At least one of the subunits may be afoundational subunit. A foundational subunit may be a subunit at itsfirst step in the process, e.g., a subunit after its initial acquiring,sourcing, or fabrication.

The system may include one or more Internet of Things (“IoT”) devices.Each of the subunits, as well as the unit, may be coupled to its owndistinct IoT device. Each IoT device may include a non-transitorycomputer memory for storing a registry of data relating to a cost and/ora quality of the unit or subunit to which it is coupled. The registry ofthe IoT device that is coupled to a foundational subunit may beinitialized with a running cost and/or a quality rating for saidfoundational subunit.

When a subunit is processed at a stage of the multi-stage supply chainprocess, the registry of the attached IoT device may be updated toreflect a change, caused by the processing at the stage, in the runningcost and/or the quality rating for the subunit.

When two or more subunits are merged into a merged component (the mergedcomponent being either another subunit or the unit) at a stage of themulti-stage supply chain process, the registry of the IoT device coupledto the merged component may be updated. Updating the registry mayinclude initializing the registry. Updating the registry may includesetting a running cost and/or the quality rating that is based at leastin part on a combination of the running costs and/or the quality ratingsof the two or more subunits.

Updating the registry may also include deactivating the IoT devicescoupled to the two or more subunits. In some embodiments, deactivatingthe IoT devices may include setting a deactivated flag for each of saidIoT devices.

When the supply chain process is complete, the registry of the IoTdevice coupled to the unit may be updated with a running cost and/or aquality rating. The update may be based on a predetermined function. Thefunction may include summing all the running costs and/or the qualityratings of every subcomponent and stage of processing that were includedin the multi-stage supply chain process.

In some embodiments of the system, each of the IoT devices may include aradio frequency identifier (“RFID”) tag. Each of the IoT devices may beconfigured to adhere to the unit or one of the subunits.

In certain embodiments, each IoT device may further include a receiverfor receiving data and a transmitter for transmitting data. The IoTdevices may be configured to transmit and receive with one or more ofthe following communication protocols: Bluetooth; IEEE 802.11 standard(“Wi-Fi”); Light Fidelity (“Li-Fi”); IEEE 802.15.4 standard (“ZigBee”);and cellular.

In some embodiments of the system, the initialized running cost for afoundational subunit may be based on a cost of obtaining thefoundational subunit. Obtaining may include purchasing, sourcing, orcreating.

The initialized quality rating for a foundational subunit may be basedon a predetermined mapping of quality ratings to a list of possiblesources of a foundational subunit. For example, a set sources may berated on a suitable scale. The scale may be 0 or 1 to 5, 10, or 100. Therating may be the result of audit, manufacturer experience, customerfeedback, research, and/or any other suitable mechanism for rating thequality of a supplier.

In certain embodiments, updating the running cost when two or moresubunits are merged may include summing the running costs of the two ormore subunits. A cost of the merging may be added to the sum. Updatingthe quality rating when two or more subunits are merged may includetaking the minimum of the quality ratings of the two or more subunits.In other embodiments, updating the quality rating may include taking anaverage of the quality ratings of the two or more subunits.

In some embodiments of the system, the IoT devices may be configured tocommunicate with each other. The updating the running cost and/or thequality rating when two or more subunits are merged into a mergedcomponent at a stage of the multi-stage supply chain process may includea sub-process. In the sub-process, the IoT device that is coupled to themerged component may communicate with the IoT devices of the two or moresubunits to receive the data stored in the IoT devices of the two ormore subunits.

Updating the running cost when a subunit is processed at a stage may, incertain embodiments, include receiving cost data from one or moresensors. The sensors may be located proximal to the stage. The cost datamay include a real-time cost associated with the stage. The cost datamay be added to the running cost.

Updating the quality rating when a subunit is processed at a stage may,in some embodiments, include receiving quality data from one or moresensors located proximal to the stage. The quality data may include areal-time quality impact associated with the stage. The quality data maybe added to the quality rating. Adding the quality data may includetaking a minimum. Adding the quality data may include taking an average.

Some embodiments of the system may include a distributed ledger for datamanagement. The distributed ledger may include a set of databases. Eachof the databases may include a set of linked data blocks. Each datablock may include hashed data. A data block that is linked to a previousdata block may include a hashing of hashed data of the previous datablock. In other embodiments, the link may be a pointer, and may notinvolve hashing.

Each one of the databases of the distributed ledger may be stored on adistinct one of a plurality of nodes. When a running cost and/or qualityrating of an IoT device is initialized/updated, a data block containingdata associated with the initialization/update may be created on each ofthe nodes. The data block may be linked to the most recent pre-updatedata block.

In some embodiments, when a running cost and/or quality rating of an IoTdevice is initialized or updated, and a data block is created on each ofthe nodes, the IoT device may transmit a signal to the nodes to triggerthe creation of the data block.

In certain embodiments, the system may further include a network of hubdevices. Each hub device may be positioned proximal to a stage of themulti-stage supply chain process. Each hub device may include an IoTreader. When an IoT device is updated at a stage, the hub device at thestage may read the data of the update from the IoT device. The hubdevice may also transmit the data of the update to the nodes forcreating a new data block.

In some embodiments of the system, the nodes may include the IoTdevices. The nodes may also include computer systems of one or morepreauthorized entities. Entities may include suppliers, manufacturers,distributers, retailers, and regulatory agencies.

A method for dynamic supply chain product valuation is provided. Themethod may include embedding each of a plurality of IoT devices across amulti-stage supply chain. The supply chain may be configured forproducing an end product from one or more sub-products.

Embedding an IoT device may include associating an IoT device with astage of the supply chain. Embedding may also include coupling an IoTdevice to a product. A product may be either the end product or one ofthe sub-products.

The method may include computing, via the IoT devices, a value impact ofeach stage of the multi-stage supply chain process.

The method may also include transmitting, via the IoT devices, eachvalue impact of a stage to a plurality of blockchain database hostsystems.

The method may further include constructing, via each of the blockchaindatabase host systems, a new linked data block for each value impact ofa stage; and

The method may also include computing a real value of the end productbased on the linked data blocks in the blockchain database host systems.

In certain embodiments, the blockchain database host systems may includethe IoT devices. The blockchain database host systems may also includecomputer systems of one or more preauthorized entities. Entities mayinclude suppliers, manufacturers, distributers, retailers, andregulatory agencies.

Certain embodiments of the system may be configured to provide real-timevaluation of components on the supply chain itself. For example, it maybe important to track the lifecycle of a component on a supply chain,such a machining tool. A particular machining tool may be rated for,e.g., a million cycles. Tracking the actual lifecycle of the particularmachining tool, may help a manufacturer replace the tool in a timelymanner, contributing to the efficiency, quality, and safety of themanufacturing process.

Some embodiments of the system may include a distributed ledger(blockchain) of records which contain information about manufacturingunits and unit assemblies (a combination of multiple units connected oraffixed into a larger unit). At the end of a supply chain, a unitassembly may represent a final product.

For example, a driver's-side airbag is a unit assembly of units(subcomponents) which themselves are assemblies of other, morefundamental or basic units. The airbag assembly is itself a unit whichmight be part of a larger assembly such as a car.

It is often desirable to understand the source of all critical unitsthat comprise a particular unit assembly. For example, for safety orquality reasons, it may be important to understand the source ofcomponents used to construct a particular driver's-side airbag, aparticular jet engine, a particular medical implant, or a particularcontainer of potato salad. Moreover, understanding the source of allcritical units may be vital in computing a real value—or cost—associatedwith the unit.

One difficulty that presents in practice is that each manufacturermaintains its own records about the source of its criticalsubcomponents. Also, within each manufacturer there exist many stages ofa supply chain process, and each stage may be associated with a variablereal cost. Calculating a real value, or a safety/quality rating, mightrequire piecing together a supply chain through many stages and/ormultiple suppliers located in different parts of the world.

One embodiment of the system may operate by allowing authorizedsuppliers of critical components to record information about thecomponent on the blockchain. The information may include cost and/orquality information. This may be done by allowing manufacturers with aprivate key to publish transactions through a wallet-like interface tothe blockchain. The information may be tied to a specific unit, forexample where the unit is identified by a serial number (“SN”). A serialnumber may be etched or printed onto the unit, or stored as anelectronic SN in a read-only memory chip. Other means of identificationsuch as specific sequences of nucleotides in a DNA or RNA fragmentencapsulated into the device body (e.g., in micro or nano-beads), orradioactively-tagged molecules.

It is envisioned that where it is not practical to identify units with aserial number or other form of ID, the “handoff” of a unit (or batch ofunits) from a supplier-manufacturer to a receiver-manufacturer andincorporation of that unit into a unit assembly by thereceiver-manufacturer can be “confirmed” by a transaction requiringagreement and joint-participation by the supplier and receiver, therebyshifting the responsibility for identifying the unit from thesupplier-manufacturer to the receiving-manufacturer. This is onlypossible where the supplier-manufacturer is providing a single unit thatis incorporated into a single unit-assembly which can be uniquelyidentified, or where the supplier-manufacturer is providing a batch ofunits (manufactured under identical conditions) which are incorporatedinto The significant information about the unit that is posted to theblockchain might include:

The ID of the unit (the identifier on the blockchain);

The serial number of the unit (or some other identifier which may applyto the discrete unit or at a batch level for multiple units fabricatedtogether under identical conditions);

An ID of the stage of manufacture;

A value impact, safety impact, and/or quality impact of a stage ofmanufacture;

The date of manufacture (or stage of manufacture);

The location of manufacture (or stage of manufacture);

The ID of the manufacturer; and

The IDs of one or more subcomponent units.

Manufacturers may submit entries to the blockchain. In some embodiments,the blockchain would be maintained in a distributed manner by at leastsome of the participants on the blockchain, including perhaps governmentregulatory agencies, consumer protection groups, etc. The verificationprocess may leverage proof-of-work or proof-of-stake, or some hybridscheme which is trusted to result in trustless verification of the entry(or block of entries) submitted to the blockchain.

Apparatus and methods described herein are illustrative. Apparatus andmethods in accordance with this disclosure will now be described inconnection with the figures, which form a part hereof. The figures showillustrative features of apparatus and method steps in accordance withthe principles of this disclosure. It is understood that otherembodiments may be utilized, and that structural, functional, andprocedural modifications may be made without departing from the scopeand spirit of the present disclosure.

FIG. 1 shows illustrative system architecture 100. Architecture 100 mayrepresent an internet of things (“IoT”). A differentiator between IoTand conventional networks is a traffic profile. In an IoT, nodes may nothave defined or known network positions, communication protocols orsecurity services. Solutions that allow architecture 100 to functionseamlessly and leverage such disparate components are disclosed herein.

Architecture 100 may include nodes. Each node may include two or morenodes. FIG. 1 shows exemplary nodes 101, 103, 105, 107 and 109. Nodes101, 103, 105, 107 and 109 may execute one or more of the functions ofthe IoT network described herein. The IoT network may include datadepository 101, data analysis engine 109 and/or actuators 107. The IoTnetwork may include any additional hardware such as receivers,transmitters, processors, databases, and any other suitable hardware.

The architecture includes sensors 103. A sensor 103 may be an IoT nodethat is a part of the IoT network disclosed herein. Sensors 103 mayinclude devices that detect changes in a physical or virtualenvironment. For example, sensors may measure audio, rainfall,temperature or water levels. Sensors may measure electronic networktraffic, electronic signals (e.g., input or output) or frequency of userlogins from within a predefined geographic area.

Sensors may be any suitable size. For example, sensors may be a fewmillimeters in size. Sensors may be deployed in a wide variety oflocations. For example, sensors may be deployed in militarybattlefields, industrial plants, in orchards, in clothing, automobiles,smart phones, jewelry or refrigerators. Sensors may be relativelyinexpensive and have low energy consumption. Sensors may “sense” two ormore stimuli or environmental changes.

Sensors may implement two or more functions. For example, sensors maymeasure changes in their native environment, capture data related to themeasured changes store and communicate the captured data. Sensors may beaccessed by other sensors or any other node. Sensors may transmitcaptured data to another node. Sensors may broadcast captured data totwo or more nodes.

Captured data may be transmitted using any suitable transmission method.For example, data captured by a sensor may be extracted by a mobilephone. Sensors may leverage a communication link provided by a mobilephone to communicate captured data to another node.

Each sensor may be a node and each sensor may be assigned a uniqueidentifier. For example, sensors may be identified by one or more radiofrequency identification (“RFID”) tags. The RFID tag may be stimulatedto transmit identity information about the sensor or any otherinformation stored on the RFID tag.

Captured data may be transmitted by the sensor and processed far fromthe location of the sensor that captured the data. For example, captureddata may be transmitted from one node to another node until the captureddata reaches data repository 101.

Sensors maybe positioned and capture data from diverse locations.Locations may be associated with stages of a supply chain. Locations mayinclude geographic locations or virtual locations on electronicnetworks. Captured data may be transmitted to a location whereinformation is needed for decisioning or consumption, which may not bethe same place the data was captured or generated. Data synchronizationprotocols and caching techniques may be deployed to ensure availabilityof information at, or delivery to, a desired node. For example, alocation where data is captured may not have continuous reliable networkconnectivity. Accordingly, captured data may be stored locally on thesensor for an amount of time prior to transmission or broadcast toanother node.

Contextually, captured data may provide information not only about thephysical environment surrounding a sensor, but the capturing of datafrom multiple sensors may provide data that signifies an event. Sensorsmay be grouped. Sensors may be grouped based on physical proximity orbased on the content (or expected content) of data captured. Sensors maybe grouped virtually. Other nodes, such as data analysis engine 109 maycreate and/or be included in such groups. In some embodiments, thecaptured data may be organized by data repository 101.

Based on data captured from sensors 103, actuators 107 may respond to adetected event. Based on the capture and analysis of multiple sources ofdata, actuators 107 may be instructed to take action without humanintervention.

Generally, sensors and other nodes that form part of architecture 100may include a processor circuit. The processor circuit may controloverall operation of a node and its associated components. A processorcircuit may include hardware, such as one or more integrated circuitsthat form a chipset. The hardware may include digital or analog logiccircuitry configured to perform any suitable operation.

A processor circuit may include one or more of the following components:I/O circuitry, which may include a transmitter device and a receiverdevice and may interface with fiber optic cable, coaxial cable,telephone lines, wireless devices, PHY layer hardware, a keypad/displaycontrol device or any other suitable encoded media or devices;peripheral devices, which may include counter timers, real-time timers,power-on reset generators or any other suitable peripheral devices; alogical processing device, which may compute data structuralinformation, structural parameters of the data, quantify indices; andmachine-readable memory.

Machine-readable memory may be configured to store, in machine-readabledata structures: captured data, electronic signatures of biometricfeatures or any other suitable information or data structures.Components of a processor circuit may be coupled together by a systembus, wirelessly or by other interconnections and may be present on oneor more circuit boards. In some embodiments, the components may beintegrated into a single chip. The chip may be silicon-based.

The node may include RAM, ROM, an input/output (“I/O”) module and anon-transitory or non-volatile memory. The I/O module may include amicrophone, button and/or touch screen which may accept user-providedinput. The I/O module may include one or more of a speaker for providingaudio output and a video display for providing textual, audiovisualand/or graphical output.

Software applications may be stored within the non-transitory memoryand/or other storage medium. Software applications may provideinstructions to the processor for enabling a node to perform variousfunctions. For example, the non-transitory memory may store softwareapplications used by a node, such as an operating system, applicationprograms, and an associated database. Alternatively, some or all ofcomputer executable instructions of a node may be embodied in hardwareor firmware components of the node.

Software application programs, which may be used by a node, may includecomputer executable instructions for invoking user functionality relatedto communication, such as email, short message service (“SMS”), andvoice input and speech recognition applications. Software applicationprograms may utilize one or more algorithms that request alerts, processreceived executable instructions, perform power management routines orother suitable tasks.

As shown in FIG. 1, a node may operate in a networked environment. Anode may be part of two or more networks. A node may supportestablishing network connections to one or more remote nodes. Suchremote nodes may be sensors, actuators or other computing devices. Nodesmay be personal computers or servers. Network connections may include alocal area network (“LAN”) and a wide area network (“WAN”), and may alsoinclude other networks. When used in a LAN networking environment, anode may be connected to the LAN through a network interface or adapter.The communication circuit may include the network interface or adapter.

When used in a WAN networking environment, a node may include a modem orother circuitry for establishing communications over a WAN, such as theInternet. The communication circuit may include the modem.

The existence of any of various well-known protocols such as TCP/IP,Ethernet, FTP, HTTP and the like is presumed, and a node can be operatedin a client-server configuration to permit a user to retrieve web pagesfrom a web-based server. Web browsers can be used to display andmanipulate data on web pages.

Nodes may include various other components, such as a battery, speaker,and antennas. Network nodes may be portable devices such as a laptop,tablet, smartphone, “smart” devices (e.g., watches, eyeglasses, clothinghaving embedded electronic circuitry) or any other suitable device forreceiving, storing, transmitting and/or displaying relevant information.

A node may include a display constructed using organic light emittingdiode (“OLED”) technology. OLED technology may enhance functionality ofa node. OLEDs are typically solid-state semiconductors constructed froma thin film of organic material. OLEDs emit light when electricity isapplied across the thin film of organic material. Because OLEDs areconstructed using organic materials, OLEDs may be safely disposedwithout excessive harm to the environment.

Furthermore, OLEDs may be used to construct a display that consumes lesspower compared to other display technologies. For example, in a LiquidCrystal Display power must be supplied to the entire backlight, even toilluminate just one pixel in the display. In contrast, an OLED displaydoes not necessarily include a backlight. Furthermore, in an OLEDdisplay, preferably, only the illuminated pixel draws power.

The power efficiency of OLED technology presents a possibility fordesigning nodes that provide enhanced security and functionality.Illustrative devices that may be constructed using OLED technology aredisclosed in U.S. Pat. No. 9,665,818, which is hereby incorporated byreference herein in its entirety.

A node may be operational with numerous other general purpose or specialpurpose computing system environments or configurations. Examples ofwell-known computing systems, environments, and/or configurations thatmay be suitable for use with the invention include, but are not limitedto, personal computers, server computers, handheld or laptop devices,tablets, “smart” devices (e.g., watches, eyeglasses, clothing havingembedded electronic circuitry) mobile phones and/or other personaldigital assistants (“PDAs”), multiprocessor systems,microprocessor-based systems, set top boxes, programmable consumerelectronics, network PCs, minicomputers, mainframe computers,distributed computing environments that include any of the above systemsor devices, and the like.

Nodes may utilize computer-executable instructions, such as programmodules, being executed by a computer. Generally, program modulesinclude routines, programs, objects, components, data structures, etc.that perform particular tasks or implement particular abstract datatypes. A node may be operational with distributed computing environmentswhere tasks are performed by remote processing devices that are linkedthrough a communications network. In a distributed computingenvironment, program modules may be located in both local and remotecomputer storage media including memory storage devices. Nodes may relyon a network of remote servers hosted on the Internet to store, manage,and process data (e.g., “cloud computing”).

Nodes may include a battery. The battery may be a power source forelectronic components of the node. For example, the battery may supplypower to the display, the communication circuit and the processorcircuit. In some embodiments, a node may include a plurality ofbatteries. Nodes may include solar panels that convert solar energy intoelectricity that powers one or more components of a node.

Sensors in a single architecture or other grouping may be produced bydifferent manufacturers. Sensors may capture data in different formats.For example, sensors may use different data structures to packagecaptured data. Sensors 103 may utilize different communication protocolsto transmit captured data or communicate with other nodes. Despite suchoperational differences, sensors 103 may operate substantiallyseamlessly together. Interoperability may allow captured data to besubstantially seamlessly captured and interpreted by data analysisengine 109. Based on interpreting the captured data, data analysisengine 109 may issue instructions to actuators 107.

Interoperability may be implemented across any suitable nodes ofarchitecture 100. Interoperability may enable communication betweensensors 103 and other nodes. Interoperability may enable architecture100 to provide services and applications via actuators 107.Interoperability may allow services and content to be provided anywhere,anytime and based on input/output of different nodes.

Data gathering by one or more of sensors 103 may be controlled by one ormore other nodes of architecture 100. For example, data analysis engine109 may control a quantity of data captured by sensors 103.Alternatively, data repository 101 and/or analysis engine 109 may filteror otherwise intelligently process data captured by sensors 103.

Timing of when data is captured by sensors 103 may be controlled by anysuitable node on architecture 100. For example, data may be captured inreal-time or at predefined intervals such as once a day. Data may alsobe captured in response to a detected environmental status change.

Data analysis engine 109 may filter data captured by sensors 103. Dataanalysis engine 103 may repackage or reformat captured data. Dataconversion may include transformation of low level raw data (possiblyfrom multiple sensors or groups of sensors) into meaningful informationfor a target audience or for a target analysis.

For example, captured data intended for human consumption or interactionmay be converted into a human understandable format. Captured dataintended for machine consumption may be converted into a format readableby a particular machine or node.

Data analysis engine 109 may perform pattern recognition to identifycorrelations and trends in captured data. Data analysis engine 109 mayalso evaluate a cost of obtaining data. “Costs” may be monetary (e.g.,labor costs or infrastructure costs), time-related or related to a levelof intrusion needed to obtain desired data. “Costs” may bebandwidth-related.

For example, a communication link may be associated with a fixedbandwidth. The bandwidth may limit an amount of information or a rate oftransmission over the communication link.

For example, a sensor may respond slowly to a request from another nodeif there is a large amount of informational traffic traveling on acommunication link shared with other nodes. The large amount ofinformational traffic may not leave sufficient bandwidth for thetransmitting node to timely communicate with the requesting node.

As a further example, a sensor may respond slowly if the sensortransmits a large amount of captured data. The large amount ofinformation transmitted by the sensor, together with other informationaltraffic traveling on the shared communication link, may be close to, orexceed the bandwidth of the communication link. As a result, sensors maybe unable to transmit captured date in a timely manner.

Data travelling within architecture 100 to/from nodes may be routedalong multiple communication links until the transmitted informationreaches a desired destination node (e.g., data analysis engine 109).Each communication link may service a number of connected nodes and arespective volume of informational traffic.

It may be difficult to ascertain available bandwidth on a particularcommunication link. It may be difficult to ascertain which communicationlinks are being utilized to transmit information between nodes. Nodesattempting to transmit information over a communication link may not beaware of a number of connected nodes, a volume of traffic on aparticular communication link or a bandwidth capacity of a communicationlink.

Furthermore, a communication link may be controlled by a differententity from an entity responsible for operation of a particular node.The entity responsible for operation of the node may be unable tomonitor a number of nodes that share a communication link, a bandwidthcapacity of a communication link or a volume of traffic transmitted on acommunication link. Despite difficult to predict conditions on acommunication link, it would be desirable for a node to timely respondto a request for information or timely receive desired information.

Sensors 103 may belong to, or operated by, differentadministrative/management domains. Sensors 103 may be operated bydifferent domains without expressly-defined relationships among suchdomains. The absence of express relationships enables access to datacaptured by sensors 103 by one or more architectures having one or morefeatures in common with architecture 100. Groups of sensors may includesensors from two or more administrative domains.

Data repository 101 may receive data captured by sensors 103. In someembodiments, data captured by sensors 103 may be transmitted directly todata analysis engine 109. Data stored in repository 101 may be sortedand analyzed by data analysis engine 109. Data stored in data repository101 may be so voluminous and complex (e.g., structured/unstructuredand/or constantly changing) that traditional data processing applicationsoftware may be inadequate to meaningfully process the data (e.g., “bigdata”). Data analysis engine 109 may include software applicationsspecially designed to process large volumes of data (“big dataanalytics”).

Based on captured data, data analysis engine 109 may optimize processes,reduce loss (e.g., fraud), improve customer understanding and targeting,increase automation, decrease latency in products and/or servicesprovided by actuators 107 and identify new analytical models that mayutilize data captured by sensors 103.

Architecture 100 may include one or more layers of softwareapplications. Software applications may implement a variety of functionsand provide varied services to nodes of architecture 100. Softwareapplications running on data analysis engine 109 may submit requests tosensors 103 for retrieval of specific data to achieve a functional goalprovided by actuators 107. Software applications may control datacaptured by sensors 103 or actions taken by actuators 107. Softwareapplications may control a flow of information within architecture 100.

Software applications may be implemented on a node. A node may be anenterprise system or a “cloud” of computing devices. On deviceapplications may be dependent on a specific hardware configuration. Suchhardware requirements may preferably be minimal, such as an extension ofthe OS/firmware of the device. For example, illustrative softwareapplications for sensors may include TinyOS, Linux, Contiki and RIOT.

Software applications may include middleware. Middleware may connect anoperating system or database to other software applications. Middlewaremay configure and manage hardware such as sensors (e.g., to achieve atarget functionality). Middleware may be responsible for aggregatingdata captured by sensors 103 and passing captured data to datarepository 101 and/or data analysis engine 109.

Software applications may provide security services that mitigatethreats to the integrity of data captured by sensors 103 or architecture100 generally.

Actuators 107 may respond to data transmitted or processed by othernodes such as data analysis engine 109. Actuators 107 may includedevices that modify the physical state of a physical entity. Actuators107 may include devices that modify a virtual state of information. Forexample, actuators 107 may move (translate, rotate, etc.) physicalobjects or activate/deactivate functionalities of more complex ones. Anactuator may dim a light bulb, open a door, change a temperaturesetting, authorize access to an automated-teller-machine (“ATM”) and/orany other suitable functionality. Actuators 107 may verify identities,trigger electronic payments, extend credit or debit accounts.

Within an intelligent networked system such as architecture 100, sensors103 perform the functions of input devices—they serve as, for example,“eyes,” collecting information about their environment. In contrast,actuators 107 act as “hands,” implementing decisions based on datacaptured by sensors 103. A single node may include the functions ofsensors and actuators.

Actuators 107 may communicate with data analysis engine 109 and sensors103. Actuators 107 may include an application programming interface(“API”) for communicating with other nodes. Actuators 107 maycommunicate directly with other nodes using machine-to-machine (“M2M”)protocols. Illustrative M2M protocols may include MQ Telemetry Transport(“MQTT”). M2M includes communication between two or more objects withoutrequiring direct human intervention. M2M communications may automatedecision and communication processes for actuators 107.

In the absence of express relationships between sensors and the devicesthat access data captured by the sensors traditional approaches formanaging trust, security naming, discovery, or other traditional networkservices may not be applicable or available. Apparatus and methodsprovided herein may provide enhanced maintenance and supervision of IoTsystems.

Generally, nodes of architecture 100 may interact and cooperate usingone or more interaction paradigms. Exemplary interaction paradigmsinclude client-server and peer-to-peer interactions.

As a result of the disparate nature of sensors 103, an architecture,such as architecture 100 incorporating sensors 103 may support a varietyof communication protocols. Illustrative supported protocols may includeHyperText Transfer Protocol (“HTTP”), Simple Object Access Protocol(“SOAP”), REpresentational State Transfer (“REST”) ConstrainedApplication Protocol (“CoAP”), SensorML, Institute of Electrical andElectronic Engineers (“IEEE”) 802.15.4 (“ZigBee”) based protocols, IEEE802.11 based protocols. For example, ZigBee is particularly useful forlow-power transmission and requires approximately 20 to 60 mW for 1 mWtransmission power over a range of 10 to 100 meters and a datatransmission rate of 250 kbit/s.

To conserve energy, a sensor may communicate wirelessly for shortperiods of time. Utilizing this approach, one or more standard sizesingle cell cylindrical dry battery batteries (e.g., AA size) mayprovide requisite computing power and wireless communication for manymonths.

Communication protocols used by nodes (e.g., sensors or actuators) maynot have, or may not be capable of having, security capabilities. Asecurity layer or buffer may be implemented by nodes that receive orrely on data captured by insecure sensors. Sensors or other nodes may bedynamically added or removed from an architecture. A security layer orbuffer may be modular to scale quickly and meet growth/contractionrequirements.

A physical layer may physically link nodes of architecture 100. Thefunction of this physical layer is to provide communication pathways tocarry and exchange data and network information between multiplesub-networks and nodes. Such communication links may be wired orwireless. Exemplary wireless communication links may include Bluetooth,Wi-Fi, 3G, 4G, 5G and LTE.

FIG. 2 shows an illustrative system with sensors 200. Sensors 200 may beIoT nodes. Sensors 200 may include one or more features of sensors 103(shown in FIG. 1). Sensors 200 include biometric sensors 203 that sensebiometric attributes. For example, biometric sensors may be embedded in“smart” clothing 209 that monitors a wearer's physical condition. Suchclothing may capture biometric data, such as pulse rate, temperature,muscle contraction, heart rhythm and physical movement. Smart clothingmay be linked to smart phone 219 such as via a Bluetooth® communicationlink. Smart phone 219 may transmit data captured by smart clothing 209to one or more other network nodes.

Biometric sensors 203 may include other illustrative sensors such asheart monitor 211, sleep monitor 213, smart watch 219, smart phone 219and automobile 215.

Sensors 200 may include personal use devices 205. Personal use devices205 may include sensors embedded in home appliances 221, productivitydevices 223 or entertainment devices 225. Productivity devices 223 mayinclude tablets, laptops or other personal computing devices.Entertainment devices may include gaming consoles and the like.

Sensors 200 also include third-party devices 207. Third-party devicesmay include devices that are not under the direct or exclusive controlof a user. A user may interact with third-party devices 207 to obtain adesired service provided by the third-party.

Exemplary third-party devices include smart card 227. Smart card 227 mayfunction as a purchasing instrument. Illustrative purchasing instrumentsmay conform to specifications published by the InternationalOrganization for Standardization. Such specifications may include:ISO/IEC 7810, ISO/IEC 7811 and ISO/IEC 7816, which are herebyincorporated herein by reference in their entireties. Suitablepurchasing instruments may include a credit card, debit card andelectronic purchasing devices. Such purchasing instruments may sense alocation or frequency of use.

Such purchasing instruments may include “EMV” chips. EMV is a technologythat derives its name from the companies (Europay, MasterCard, and Visa)that helped develop the technology. When the credit card and itsassociated EMV chip are inserted into a specialized card reader (anothersensor), the reader powers the EMV chip and the EMV chip generates a newauthorization code each time the credit card is used. The EMV chip maycapture transaction data such as amounts, location or identity of thechip reader.

Third-party sensors 207 may include ATMs 229 and point-of-sale terminals(“POS”) 231. Such devices may also be actuators.

Third-party devices may also include software applications 233.Applications 233 may be used to access services, such as an onlinebanking portal. Such applications may detect biometric features toauthorize access to the online banking portal. Third-party devices mayinclude sensors that capture data associated with power consumption(e.g., smart grids), electronic communication traffic, logistics(package movement) or any other suitable environmental condition.

FIG. 2 shows that sensors may categorically overlap. For example, anapplication used to access an online bank portal may capture a biometricfeature (e.g., fingerprint) to authenticate a user.

Each of the sensors shown in FIG. 2 may include different and possiblyincompatible hardware. For example, sensors may each have differentoperating systems (or none at all), processor types and memory. Sensors200 may be inexpensive, single-function devices with rudimentary networkconnectivity. Sensors 200 may be positioned in remote and/orinaccessible locations where human intervention or configuration isdifficult.

To conserve power, sensors 200 may utilize 16-bit microcontrollers. Suchmicrocontrollers may use less than 400 μW per MIPS (“millioninstructions per second”) and may be capable of operating TCP/IPv6stacks with 4 kB RAM and 24 kB flash memory. As outlined in proposedInternet standard RFC 4944, which is hereby incorporated by reference inits entirety, IPv6 may be implemented over IEEE 802.15.4 (e.g., ZigBee)based wireless communication protocols or other suitable communicationprotocols.

Furthermore, because of potentially disparate features andcharacteristics of sensors 200, security solutions disclosed herein maybe used to verify an authenticity of a sensor and/or data transmitted bythe sensors.

FIG. 3 shows illustrative system 300. System 300 may include a smartsupply chain. The smart supply chain may include Entity 1, 301, Entity2, 303, Entity 3, 305, and Entity 4, 307. An example of an entity mayinclude a manufacturer or a supplier.

In one embodiment, Entity 4 (307) may procure Component 1 (309) fromEntity 1 (301), Component 2 (311) from Entity 2 (303), and Component 3(313) from Entity 3 (305). Each of Entities 1-3 (301-305) may haveprocured its respective component via sourcing, fabricating, purchasing,or any other suitable means for procuring a component. The procuring maybe a one step process, or, alternatively, a multi-step process.

Entity 4 may manufacture an end product 315 from Components 1-3.Manufacturing end product 315 may include merging Components 1-3. Themanufacturing may be a one step process, or, alternatively, a multi-stepprocess.

In some embodiments of the system, the smart supply chain may include aplurality of IoT devices (not shown). The IoT devices may be attachedto, or otherwise associated with, Components 1-3 and end product 315.

For example, a first IoT device may be attached to Component 1. Entity 4(307) may attach the first IoT device upon procuring Component 1. Thefirst IoT device may be initialized with a first cost, C₁. C₁ may be thecost of procuring Component 1. A second IoT device may be attached toComponent 2. The second IoT device may be initialized with a secondcost, C₂. C₂ may be the cost of procuring Component 2. A third IoTdevice may be attached to Component 3. The third IoT device may beinitialized with a third cost, C₃. C₃ may be the cost of procuringComponent 3.

Entity 4 (307) may merge Components 1-3 to form end product 315. Themerging may be associated with a fourth cost, C₄. A fourth IoT devicemay be attached to end product 315. The fourth IoT device may contain afinal cost, C_(f). C_(f) may be computed by summing C₁-C₄, to provide anactual, fact-based valuation of end product 315. In some embodiments,the fourth IoT device may compute C_(f) directly. The direct computationmay include receiving a transmission of cost data (C₁-C₃) from thefirst, second, and third IoT devices. In some embodiments, the first,second, and third IoT devices may be deactivated after transmitting thecost data, in effect being subsumed by the fourth—more cumulative—IoTdevice. The fourth IoT device may receive C₄ via sensors, another IoTdevice proximal to the merging, a computer system associated with Entity4, or any other suitable source.

Entity 4 (307) may leverage C_(f) to conduct fact-based, real-time,supply chain analytics. The supply chain analytics provided by thesystem may be used to find strengths and weaknesses within the supplychain. The supply chain analytics provided by the system may be used fordynamic pricing and cost sharing that reflect a real value of endproduct 315.

In some embodiments, the supply chain analytics provided by the systemmay be useful for custom builds. New or additional features and/orcomponents can may be accurately tacked on the standard, real valueprice to give the user a clear and precise price point. Similarly, abuyer may leverage the system to choose to reject an option or limitadditional features and/or components due to their budget or otherfactors. A manufacturer may also be able to give more accurateassessments of bulk orders to maximize profit while giving a fair marketvalue.

In some embodiments, the first, second, and third IoT devices may beattached at and/or by Entities 1-3, respectively. In certainembodiments, the IoT devices may include safety and/or qualityinformation to provide a real-time, fact-based, safety and/or qualityrating.

FIG. 4 shows illustrative system 400. System 400 may include a smartsupply chain. The smart supply chain may include Entity 1. System 400may show a part of a multi-stage process for manufacturing an endproduct. The process may begin at stage 401. Stage 401 may include animprovement to Component 1. The same Component 1 may be subject to stage403, etc., until the process culminates at stage 405 to produce the endproduct.

An IoT device (not shown) may, in some embodiments, be attached toComponent 1 at or prior to stage 401. The IoT device may be initializedwith a cost. The initial cost may be a cost of purchasing, sourcing, orfabricating Component 1. The cost stored in the IoT device may beupdated at each stage to reflect a cost associated with that stage. Forexample, the IoT device may be initialized with a purchase cost of $100.Stage 401 may include painting Component 1. The painting may cost $10,so the IoT device may be updated to store a running cost of $110. Stage405 may include applying a sealant to complete Component 1. The runningcost may be updating by adding $15—the cost of applying the sealant—fora total real cost of $125.

In other embodiments, IoT devices may be associated with some or all thestages of the supply chain. The IoT devices may track the progress of acomponent through the stages of the supply chain to provide a dynamicvaluation of end products.

FIG. 5 shows illustrative system 500. System 500 may include a smartsupply chain. The smart supply chain may include Entity 1, 501, Entity2, 503, Entity 3, 505, and Entity 4, 507. An example of an entity mayinclude a manufacturer or a supplier. The entities may, in someembodiments, be related sub-entities under a larger, umbrella, entity.

In one embodiment, Entity 4 (507) may procure Component 1 from Entity 1,Component 2 from Entity 2 (503), and Component 3 from Entity 3 (505).Each of Entities 1-3 (501-505) may have procured its respectivecomponent via sourcing, fabricating, purchasing, or any other suitablemeans for procuring a component. The procuring may be a one stepprocess, or, alternatively, a multi-step process. A multi-step processmay be shown at Entity 1 (501) where Component 1 progresses from step509 to 511.

Entity 4 may manufacture an end product 521 from Components 1-3.Manufacturing end product 521 may first include merging Components 1 and2 at step 517. Step 519 may further process the merged component. Atstep 521, the merged component may be further merged with Component 3 toform the end product.

In some embodiments of the system, the smart supply chain may include aplurality of IoT devices. The IoT devices may be attached to, orotherwise associated with, Components 1-3 and the end product.

For example, a first IoT device IoT1 may be attached to Component 1.IoT1 may be initialized with a first cost, C₁. C₁ may be the cost ofprocuring Component 1. C₁ of IoT1 may be updated at step 511 to storeCr. A second IoT device, IoT2, may be attached to Component 2. IoT2 maybe initialized with a second cost, C₂. C₂ may be the cost of procuringComponent 2. A third IoT device, IoT3, may be attached to Component 3.IoT3 may be initialized with a third cost, C₃. C₃ may be the cost ofprocuring Component 3.

Entity 4 (507) may merge Components 1 and 2 at step 517. A fourth IoTdevice, IoT4, may be attached to the merged component. IoT4 may beinitialized with a cumulative cost, C_(c1), that includes a sum ofC_(1′), C₂, and a cost of the merge, C_(m1). Entity 4 may furtherprocess the merged component at step 519. IoT4 may be updated with acost that includes a cost of the further processing, to yield C_(c1′).At step 521, Entity 4 may further merge the merged component withComponent 3 to form the end product. A fifth IoT device, IoT5, may beattached that stores a final cost, C_(f). C_(f) may include a sum ofC_(c1′), C₃, and a cost of the final merge.

In some embodiments, the IoT devices may communicate among each otherdirectly to compute the running costs. In some embodiments, the first,second, third, and fourth IoT devices may be deactivated aftertransmitting the cost data to the more cumulative IoT devices, in effectbeing subsumed by the more cumulative IoT devices.

In certain embodiments, the IoT devices may be configured to be repairedand/or adjusted based on real-time conditions. This feature may allowfor autonomous operations and recovery. Furthermore, the IoT devices maybe configured to detect quality from a previous device to understand anddetect failure rates. For example, IoT3 may sense an increasing errorrate from IoT2. This may indicate an upstream error, e.g., from IoT1, orthat IoT2 may be compromised.

FIG. 6 shows illustrative system 600. System 600 may include a smartsupply chain. The smart supply chain may, in an exemplary embodiment,include Stage 1, 601, Stage 2, 603, etc., until Stage n, 605. Any numberof stages may exist between Stage 2 and Stage n. Stages 601-605 may bepart of a multi-stage process for manufacturing an end product.

Stages 601-605 may each be associated with an IoT device, 607-611. IoTdevices 607-611 may include sensors for deriving a cost associated witha stage. For example, an IoT device at a stage may include a cameraconnected to a processor. The IoT device may measure that 10 gallons ofwhite paint were used to paint a component. The IoT device may haveaccess to a database that contains a price per gallon of white paint.Thus, the IoT device may compute a cost for the stage. If, for example,2 gallons of paint spill on the floor, thereby necessitating 12 gallonsfor the painting of a particular component, the IoT device will adjustthe cost of the stage for that particular component accordingly.

In certain embodiments, IoT devices 607-611 may include IoT readers. TheIoT readers may scan passing components and receive data stored on thecomponents. For example, the components may include RFID tags attachedto them. The RFID tags may store cost information. The IoT readers mayread the cost information from the RFID tags.

IoT devices 607-611 may transmit the computed costs to a database. Insome embodiments, the database may be a server, or a central database ofan entity. In other embodiments, the database may be a distributedledger, or a blockchain database.

FIG. 7 shows illustrative flowchart 700. Flowchart 700 may show anexemplary process for an IoT device-based, dynamic supply chainvaluation system.

Flowchart 700 begins with step 701. At step 701, an IoT device connectedto a component is initialized with a value. The value may be a runningcost or a quality/safety rating of the component. At a stage of amulti-stage supply chain, the value in the IoT device may be updated, atstep 703, to reflect a change in the value that occurred at the stage.Step 705 queries whether the component is merged with another componentto form a merged component. If it is merged, then at step 707 the IoTdevice contributes its data (i.e., the value) to a cumulative IoT devicethat is attached to the merged component. Contributing data may includetransmitting the data directly to the other IoT device. The IoT devicemay be deactivated at step 709. Since the cumulative IoT device is a newIoT device attached to a new, merged, component, the process for thecumulative IoT device may recursively feed back into step 701,initializing. Initializing the cumulative IoT device may includereceiving the data contributed by the IoT devices at step 707.

If the component at step 705 is not merged, the process queries whetherthe stage is the final stage, and therefore the component is now the endproduct. If not, the process loops back to step 703 for the next stage.If yes, the real, final value is computed at step 713, and the processis complete. Thus, the process runs a recursive algorithm which computesa cumulative result for an end product based on narrower computationsexecuted by IoT devices connected to smaller sub-components.

FIG. 8 shows illustrative system 800. System 800 shows an exemplaryblockchain database for use in conjunction with a smart supply chain.

System 800 may include a plurality of nodes. The nodes may include Node1 (801), Node 2 (803), etc., through Node n (805). Each of nodes 801-805may store a copy of a tree-like data structure. Each of nodes 801-805may independently receive data to store in its data structure. The nodesmay compare their data structures among each other and coordinate—i.e.,sync—the data structures based on a consensus or a quorum.

The data structure hosted by nodes 801-805 may include blocks 807-817.Blocks 807-817 may include data associated with a multi-stage supplychain process for a particular end product. Each block may, in thissimple example, store a stage ID number and a cost. (In thisillustrative example, the cost is the cost for each stage individually.In other embodiments, the cost may be a running cost, i.e., a summationof the costs of the current and previous stages.) Block 807 may store #1for stage ID number, and $4.01 for a cost of the stage. Stage 1 mayinclude purchasing a sub-component, and the purchase price in thisparticular instance may have been $4.01. Blocks 809 and 811 mayrepresent that stages number 2 and 3, respectively, cost $6.42 and$2.17.

Blocks 813 and 815 may represent that stages number 4 and 5,respectively, cost $8.74 and $0.17. Stages 4 and 5 may represent aprocess with a different sub-component than the sub-component of stages1-3. Block 817 may represent stage 6, at which the two sub-componentsmay be merged, with an associated cost of $5.00. A total cost may becomputed for the end product by summing the cost in each block. In thisexample, the total cost for the end product is $26.51.

In some embodiments, the blocks may be linked in a linear fashion. Forexample, when the sub-components are merged at stage 6, blocks 813 and815 may be appended after block 811, and block 817 may be appended afterblock 815. In some embodiments, the data in blocks 807-817 may be hashedand/or encrypted.

The steps of methods may be performed in an order other than the ordershown and/or described herein. Embodiments may omit steps shown and/ordescribed in connection with illustrative methods. Embodiments mayinclude steps that are neither shown nor described in connection withillustrative methods.

Illustrative method steps may be combined. For example, an illustrativemethod may include steps shown in connection with another illustrativemethod.

Apparatus may omit features shown and/or described in connection withillustrative apparatus. Embodiments may include features that areneither shown nor described in connection with the illustrativeapparatus. Features of illustrative apparatus may be combined. Forexample, an illustrative embodiment may include features shown inconnection with another illustrative embodiment.

The drawings show illustrative features of apparatus and methods inaccordance with the principles of the invention. The features areillustrated in the context of selected embodiments. It will beunderstood that features shown in connection with one of the embodimentsmay be practiced in accordance with the principles of the inventionalong with features shown in connection with another of the embodiments.

One of ordinary skill in the art will appreciate that the steps shownand described herein may be performed in other than the recited orderand that one or more steps illustrated may be optional. The methods ofthe above-referenced embodiments may involve the use of any suitableelements, steps, computer-executable instructions, or computer-readabledata structures. In this regard, other embodiments are disclosed hereinas well that can be partially or wholly implemented on acomputer-readable medium, for example, by storing computer-executableinstructions or modules or by utilizing computer-readable datastructures.

Thus, methods and apparatus for blockchain augmented internet of things(“IoT”) device-based systems for dynamic supply chain tracking areprovided. Persons skilled in the art will appreciate that the presentinvention can be practiced by other than the described embodiments,which are presented for purposes of illustration rather than oflimitation, and that the present invention is limited only by the claimsthat follow.

What is claimed is:
 1. A smart supply chain (“SSC”), the SSC comprising:a plurality of stages, each stage configured to execute one step of amulti-step process for producing an end product from one or moresub-products; a plurality of Internet of Things (“IoT”) devices, atleast one of the IoT devices that is associated with a stage and atleast one of the IoT devices that is coupled to a product, said productbeing either the end product or one of the sub-products; and ablockchain database, said blockchain database comprising a plurality ofcoordinated databases, wherein each coordinated database is stored on adistinct node of a plurality of nodes, and each coordinated databasecomprises linked blocks of hashed data, wherein a block that is linkedto a previous block includes a hashing of the hashed data of theprevious block; wherein: the IoT devices compute a record for each stepof the multi-step process, said record comprising data that includes astep identifier (“ID”) and a calculation of a value impact of the step;the data is added to the blockchain database; and the end product isassociated with a real value that is based on the data in the blockchaindatabase.
 2. The SSC of claim 1, wherein the value impact of a stepincludes: a sum of the values of a plurality of sub-products that aremerged at the step; an increase in value due to an improvement executedon a product at the step; and a decrease in value due to an occurrenceat the step.
 3. The SSC of claim 1, wherein, when an IoT device computesa record for a step, the IoT device adds the data of the record to theblockchain database by transmitting the data to the plurality of nodes,and each node hashes the data and stores the hashed data as a new linkedblock.
 4. The SSC of claim 1, wherein each one of the IoT devices is anode.
 5. The SSC of claim 1, wherein the nodes comprise computer systemsof one or more preauthorized entities of the following list of entities:suppliers; manufacturers; distributers; retailers; and regulatoryagencies.
 6. A system for dynamic valuation of a unit, said unit that ismanufactured via a multi-stage supply chain process, and said unit thatcomprises one or more subunits, at least one of the subunits being afoundational subunit, the system comprising one or more Internet ofThings (“IoT”) devices, wherein: each of the subunits and the unit arecoupled to a distinct IoT device of the IoT devices; each IoT devicecomprises a non-transitory computer memory for storing a registry ofdata relating to a cost and a quality of the unit or subunit to whichsaid IoT device is coupled; the registry of the IoT device that iscoupled to a foundational subunit is initialized with a running cost anda quality rating for said foundational subunit; when a subunit isprocessed at a stage of the multi-stage supply chain process, theregistry of the IoT device coupled to said subunit is updated to reflecta change, caused by the processing at the stage, in the running cost andthe quality rating for said subunit; when two or more subunits aremerged into a merged component, at a stage of the multi-stage supplychain process: the registry of the IoT device coupled to the mergedcomponent is updated with a running cost and quality rating that arebased at least in part on a combination of the running costs and thequality ratings of the two or more subunits; and the IoT devices coupledto the two or more subunits are deactivated; and when the supply chainprocess is complete, the registry of the IoT device coupled to the unitis updated with the running cost and the quality rating that are basedon a predetermined function of all the running costs and the qualityratings of every subcomponent and stage of processing that were includedin the multi-stage supply chain process; wherein the system furthercomprises: a distributed ledger for data management, said distributedledger comprising a set of databases, each of said databases comprisinga set of linked data blocks, each data block comprising hashed data,wherein a data block that is linked to a previous data block includes ahashing of hashed data of the previous data block, and each one of saiddatabases is stored on a distinct one of a plurality of nodes, wherein:when a running cost and quality rating of an IoT device are initialized,a data block containing data associated with the initialization iscreated on each of the nodes; and when a running cost and quality ratingof an IoT device are updated, a data block containing data of the updateis created on each of the nodes, and said data block is linked to themost recent pre-update data block.
 7. The system of claim 6, whereineach of the IoT devices comprises a radio frequency identifier (“RFID”)tag, and each of the IoT devices is configured to adhere to the unit orone of the subunits.
 8. The system of claim 6, each IoT device furthercomprising a receiver for receiving data and a transmitter fortransmitting data, wherein the IoT devices are configured to transmitand receive with one or more of the following communication protocols:Bluetooth; IEEE 802.11 standard (“Wi-Fi”); Light Fidelity (“Li-Fi”);IEEE 802.15.4 standard (“ZigBee”); and cellular.
 9. The system of claim6, wherein: the initialized running cost for a foundational subunit isbased on a cost of obtaining the foundational subunit, said obtainingcomprising purchasing, sourcing, or creating; and the initializedquality rating for a foundational subunit is based on a predeterminedmapping of quality ratings to a list of possible sources of afoundational subunit.
 10. The system of claim 6, wherein: the updatingthe running cost when two or more subunits are merged comprises summingthe running costs of the two or more subunits, and adding to the sum acost of the merging; and the updating the quality rating when two ormore subunits are merged comprises taking the minimum of the qualityratings of the two or more subunits.
 11. The system of claim 6, whereinthe deactivating of the IoT devices of the two or more subunitscomprises setting a deactivated flag for each of said IoT devices. 12.The system of claim 6, wherein the IoT devices are configured tocommunicate with each other, and the updating the running cost and thequality rating when two or more subunits are merged into a mergedcomponent at a stage of the multi-stage supply chain process comprises asub-process wherein the IoT device that is coupled to the mergedcomponent communicates with the IoT devices of the two or more subunitsto receive the data stored in the IoT devices of the two or moresubunits.
 13. The system of claim 6, wherein: the updating the runningcost when a subunit is processed at a stage comprises receiving costdata from one or more sensors located proximal to the stage, said costdata including a real-time cost associated with the stage, and the costdata is added to the running cost; and the updating the quality ratingwhen a subunit is processed at a stage comprises receiving quality datafrom one or more sensors located proximal to the stage, said qualitydata including a real-time quality impact associated with the stage, andthe quality data is added to the quality rating.
 14. The system of claim6, wherein, when a running cost and quality rating of an IoT device areinitialized or updated, and a data block is created on each of thenodes, said IoT device transmits a signal to the nodes to trigger thecreation of the data block.
 15. The system of claim 6, furthercomprising a network of hub devices, each hub device positioned proximalto a stage of the multi-stage supply chain process, and each hub devicecomprising an IoT reader, wherein, when an IoT device is updated at thestage, the hub device reads the data of the update from the IoT device,and transmits the data of the update to the nodes for creating a newdata block.
 16. The system of claim 6, wherein the nodes comprise theIoT devices.
 17. The system of claim 6, wherein the nodes comprisecomputer systems of one or more preauthorized entities of the followinglist of entities: suppliers; manufacturers; distributers; retailers; andregulatory agencies.
 18. A method for dynamic supply chain productvaluation, the method comprising: embedding each of a plurality ofInternet of Things (“IoT”) devices across a multi-stage supply chainthat is configured for producing an end product from one or moresub-products, wherein said embedding comprises associating an IoT devicewith a stage or coupling an IoT device to a product, said product beingeither the end product or one of the sub-products; computing, via theplurality of IoT devices, a value impact of each stage of themulti-stage supply chain process, wherein computing the value impact ofa stage comprises computing a change, caused by processing at the stage,in a running cost and a quality rating for said product; transmitting,via the plurality of IoT devices, each value impact of a stage to aplurality of blockchain database host systems; constructing, via each ofthe plurality of blockchain database host systems, a new linked datablock for each value impact of a stage; and computing a real value ofthe end product based on the linked data blocks in the plurality ofblockchain database host systems.
 19. The method of claim 18, whereinthe plurality of blockchain database host systems comprise the IoTdevices and computer systems of one or more preauthorized entities ofthe following list of entities: suppliers; manufacturers; distributers;retailers; and regulatory agencies.